Received: by mail2.netcom.com (8.6.9/Netcom) id WAA13913; Sat, 27 Aug 1994 22:53:14 -0700
Received: from nova.unix.portal.com by mail2.netcom.com (8.6.9/Netcom) id WAA13895; Sat, 27 Aug 1994 22:53:09 -0700
From: Jeric@cup.portal.com
Received: from hobo.corp.portal.com (hobo.online.portal.com [156.151.5.5]) by nova.unix.portal.com (8.6.7/8.6.4) with ESMTP id WAA07505 for <lightwave-l@netcom.com>; Sat, 27 Aug 1994 22:52:36 -0700
Received: from localhost (pccop@localhost) by hobo.corp.portal.com (8.6.4/1.60) id WAA23788 for lightwave-l@netcom.com; Sat, 27 Aug 1994 22:52:35 -0700
To: lightwave-l@netcom.com
Subject: Re: LW questions
Lines: 33
Date: Sat, 27 Aug 94 22:52:34 PDT
Message-ID: <9408272252.3.23286@cup.portal.com>
X-Origin: The Portal System (TM)
Sender: owner-lightwave-l@netcom.com
Precedence: bulk
Reply-To: lightwave-l@netcom.com
>Use Shift All Keys to move everything later in time. The only
>tricky part is dealing with the keys at frame zero, but you can copy
>them with the above procedure if needed.
True, but it always seemed to me it might be nice if the Frame Zero
keys were automagically duplicated by the shift function.
Man am I lazy!
I guess this might screw up spline motions though.
>>>>>>>>>>>>>>
On another topic, would it be possible to implement "Cycle Motions"
that DONT's start at Frame Zero? This is a recurring problem
when making cloned objects that have identical, yet temporally
offset cyclic motions.
Maybe a simple "OFFSET" parameter in the Motion Requestor would